Problem Note 51194: When you use SASINITIALFOLDER options in a SAS® program that resides on the network, you might not be able to connect to the database
If the SASINITIALFOLDER option is set to a network path such as -sasinitialfolder \\network\folder, the following error might occur when you connect to an Oracle or Teradata database:
ERROR: The SAS/ACCESS Interface to ORACLE cannot be loaded.
ERROR: Image SASORA found but not loadable. Please make sure Oracle environment is set correctly.
The error below appears in the log when you try to assign a LIBNAME to Teradata and the SASINITFOLDER option is set to a network drive:
ERROR: The SAS/ACCESS Interface to Teradata cannot be loaded.
The SASTRA code appendage could not be loaded
An error similar to the one above could occur if the SAS program that is used to connect to a database resides on a network drive and you try to run the program as a batch job. The program runs without any problem if your current directory path is a local drive or you are running in interactive mode.
To resolve the problem, follow these steps:
Warning: Changes in the Windows registry can render your system unusable and require that you reinstall the operating system. Always back up your registry before you make any registry changes. For assistance, see Windows Help, Microsoft documentation, or the Microsoft Windows website. SAS is not responsible when you edit the Windows registry.
- Open the Windows Registry Editor:
- Select Start ► Run.
- Enter regedit in the search box.
- Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths.
- Look for the key SAS.EXE. There are two entries under SAS.EXE. Remove the quotation marks from the beginning and end of the paths for both entries.
- Reboot your machine, invoke SAS, and try connecting to your database.
Operating System and Release Information
| SAS System | SAS/ACCESS Interface to Oracle | Microsoft® Windows® for x64 | 9.3_M1 | 9.4_M1 | 9.3 TS1M1 | 9.4 TS1M1 |
| Microsoft Windows Server 2003 Datacenter Edition | 9.3_M1 | | 9.3 TS1M1 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.3_M1 | | 9.3 TS1M1 | |
| Microsoft Windows Server 2003 Standard Edition | 9.3_M1 | | 9.3 TS1M1 | |
| Microsoft Windows Server 2003 for x64 | 9.3_M1 | | 9.3 TS1M1 | |
| Microsoft Windows Server 2008 | 9.3_M1 | | 9.3 TS1M1 | |
| Microsoft Windows Server 2008 R2 | 9.3_M1 | 9.4_M1 | 9.3 TS1M1 | 9.4 TS1M1 |
| Microsoft Windows Server 2008 for x64 | 9.3_M1 | 9.4_M1 | 9.3 TS1M1 | 9.4 TS1M1 |
| Windows 7 Enterprise 32 bit | 9.3_M1 | | 9.3 TS1M1 | |
| Windows 7 Enterprise x64 | 9.3_M1 | | 9.3 TS1M1 | |
| Windows 7 Home Premium 32 bit | 9.3_M1 | | 9.3 TS1M1 | |
| Windows 7 Home Premium x64 | 9.3_M1 | | 9.3 TS1M1 | |
| Windows 7 Professional 32 bit | 9.3_M1 | | 9.3 TS1M1 | |
| Windows 7 Professional x64 | 9.3_M1 | 9.4_M1 | 9.3 TS1M1 | 9.4 TS1M1 |
| Windows 7 Ultimate 32 bit | 9.3_M1 | | 9.3 TS1M1 | |
| Windows 7 Ultimate x64 | 9.3_M1 | | 9.3 TS1M1 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Data Sources ==> External Databases ==> Oracle
Data Management ==> Data Sources ==> External Databases
|
| Date Modified: | 2013-10-04 17:01:48 |
| Date Created: | 2013-09-27 16:46:18 |
